2.5.141 Maintenance Release Notes

In This Topic...

Enhancements

  • Billing data has now been made available to the latest transactions in a policy. Previously, billing data was only available for the New Business and Renewal transactions in a given policy term as these are the "main" transactions, however, this made it difficult for users working in subsequent transactions to retrieve this data without having to navigate to those original transactions, specifically when configuring auto cancellations.

    Now, the following core billing fields are available for the latest transactions in a policy:

    • BillingPolicyTermCollectedAmount
    • BillingPolicyTermOutstandingAmount
    • BillingPolicyTermEarliestOverdueInvoiceDueDate
    • BillingPolicyTermOverdueAmount
    • BillingPolicyOutstandingAmount
    • BillingPolicyRemainingUnpaidAmount
    • BillingTotalTransactionPaymentAmount

  • The Bridge system now stores the data from the Source and Source Reference columns in the General Ledger Entry Report, in the database. This change will make this information available for reporting in order to clearly distinguish between events that result in Posting a Cash Receipt or moving the OAB amounts within billing.

  • Previously, when using the ImportBatchReceipt web service to import batch receipts for policies that had an Effective Date set in the future, the settings for Receipt Detail Allocation were not being applied properly. The web service was missing a validation for the Apply when Policy Term is effective setting when set to active, and the cash amounts were being applied to the invoices instead of the amount being transferred to the On Account Balance of the Bill to Party. An enhancement has been added to validate if the policy term is effective in the future or not. If the policy term is effective with a future date, the system removes the receipt allocation data as per the Billing setting.

  • To aid users when building Billing dashboards, an enhancement has been made to allow direct access to a Bill to Party from a configured hyperlink in a dashboard. Previously, to access a Bill to Party, the user had to select the Billing Entity first or an error message could be returned. After this enhancement, the Bill to Party can be accessed independent of its Billing Entity.

  • Previously, the system did not show the details of the Cash Receipt Allocation when the system used the automatic On Account Balance to pay the outstanding invoices. A new Type column has been added to the Refund/on Account Allocation panel to show whether it is a Refund or Account Balance Allocation type. Additionally, each receipt in the On Account allocation will hyperlink to the Receipt Information screen.

    Please note that the Refund panel name has been changed to Refund/on Account allocation.

Bug Fixes

  • When initiating a Cancel Re-write, the premium and commission amounts would have the incorrect values in the Distributor Commission by Premium Type grid. This issue only occurred for direct bill policies when a user imported a policy via web service. A code fix has been implemented, and the proper premium and commission amounts now generate.

  • The On Account Balance amounts were not being applied to policy invoices automatically when a cash receipt is linked to the Invoice and there are no Future Charges in the Booked status for the Policy Term. The issue has been resolved by a code change.

  • Previously, values from a custom Client fields were not being saved in a quote or new transaction. This occurred when the Company Information was updated/changed for an Assured company. The process responsible for validating if there are changes to custom client fields was not running and therefore returned false, and replaced the new values with previously saved custom field values. A code update has been implemented that will now check for field modifications, and values for custom client fields are successfully saved.

  • Previously, for the ImportPolicy web service, if a policy contained a custom field with the Field Mapping Rule for Endorsement set to Copy From Source for a custom field, the default values from the custom field would not copy to the subsequent Endorsement. Instead, the subsequent Endorsement would contain incorrect or blank field values. This problem occurred because there was no logic in the code to copy Field Mapping Rules for the default values of custom fields. A code fix has been implemented so that policies with custom field default values now copy to subsequent transactions when importing via web service.

  • Previously, when a batch receipt was imported to the Bridge Specialty Suite for a policy that had multiple terms, the system did not allocate the On Account Balance (OAB) premium amount to the policy term. Instead, the system allocated the OAB to the Bill To Party. This occurred because the Web Service checked the Policy Number rather than the TermID. Since the policy number could be the same for different policy terms, the system could not allocate the charges to their respective terms. A new node for TermID has been added in the ImportBatchReceipt web service to check TermIDs when allocating OAB so that the imported policies will have their premium amount allocated to future charges accordingly.

  • Previously, when stepping through a submission, a server error message could appear instead of displaying the next screen in a submission workflow. This error occurred in a submission where a row had been added to a grid with formulas and then deleted. bug fix has been implemented to the Formula Evaluator so that users can proceed in the submission without an error message.

  • Claims: Previously, when users created a First Notice of Loss, the Claim created by field and CreatorLogonId were not being populated by the system. A fix has been implemented and the field values are now correctly populated and available for use on-screen and in documents.

  • Previously, when creating new transactions on a policy term, an Assured/Insured Company attached to the previous transaction would not carry forward into the new transaction if the company Code contained spaces. As a result, the company details in the Insured widget would appear empty after carrying forward the transaction. A code fix has been implemented to ensure a company is carried forward into new transactions, as expected.

  • Previously, a server error appeared when trying to create an Endorsement on a policy with a file loaded for the File Upload Control that had an out-of-sequence Endorsement. This server error occurred when file upload contents were loaded during the field copying and the GUID of the loaded files did not match what was saved in the TransactionXML. A code fix to prevent this error has been implemented, in which a link is placed upon the file uploaded rather than the deleted file. As a result, the error message no longer appears.

  • Previously, in a custom field, the Default Formula of a Calculated Field could not be pushed to the Field Path of the Bind To section. This bug occurred when a field was configured as non-calculated and contained BindTo set to a standard field such as Claim/DateofLoss or Policy/MasterCover. As a result, the field value would not be updated during a Save event. A bug fix has been implemented and non-calculated fields can now be bound to Standard Fields.

  • Previously, an Office Admin user would see the Policy Term displayed in the Submission/Policy List screen, but they would not see the term's Audit Trail. This occurred because the logic used to validate the scope in the Policy Search was different from that of the Audit Trail screen. A fix has been implemented in which the Policy Transaction scope is used for both the Audit Trail screen and the Policy Transaction scope.

  • Previously, the Data Table Web Service failed if the data contained an Ampersand (&). Following the 2.5.140 release, the Ampersand (&) will be encoded in the data and can be included in the Data Table Web Service.

  • Previously, when filtering Data Sources in the Data Source Configuration Management screen, a bug occurred when the columns of a Data Source used a Field or Constant Value containing code that was different from the Column code. As a result, the filters were not applied, and the WebAPI call returned every result. A code fix has been implemented, and Data Source returns now properly returns filtered results.

  • Previously, any user could call a method for Insurity Bridge Common API via Insurity Azure Gateway. Now, a fix has been implemented that allows only authorized users to call a method. If a user is not authorized, an error message will display "Error: Unauthorized User" after entering the field for user authorization.

    Note: For details, please contact your Insurity representative

  • Previously, General Ledger entries could have an Entry Date of a past Receipt Date after setting Reserve On Account Amount to Future Installments to No in the On Account Balance screen. Now, the date will update according to when the setting Reserve On Account Amount to Future Installments has been set to No.

  • Previously, when generating and manually invoicing a Premium Refund, additional General Ledger entries of Written Premium and Premium Account Receivables were created for the Premium Refund invoice. This occurred when users created, generated, and bound a direct bill policy with taxes and commission values, generated an invoice, and flat canceled the policy. Now, for this case, the two additional General Ledger entries of Written Premium and Premium Account Receivables are no longer created.

  • Previously, when users used the ContainsUserRole()function in a Calculated Field in a Policy Workflow, altered the assigned security role for a user, and published the workflow, the change in User Roles would not update timely in the User Profile. This occurred because roles are only updated when the User Name, First Name, and Last Name for the logged in user are empty. Now, roles are updated whenever there is a change or modification to a User Role.

  • Previously, once a New Business Transaction was created, quoted and bound with Deductible Charges applied, the newly created Deductible Invoice would not be available for selection in the Batch Receipt List grid for a Batch Receipt. A code fix has been implemented, and deductible invoices are now available in the Batch Receipt List grid upon creating a Deductible Charge.

  • Previously, if an Assured company code contained special characters, the company was not carried onto subsequent transactions. As a result, the newly created transaction would be without an Assured company. A fix has been implemented where special characters are encoded to be compatible with allowed characters in the URL, and the Assured code is then decoded for the Bridge API. Now the Assured code can be found successfully, and Assured code can be carried forward to subsequent transactions.

  • Previously, when users created an Out-of-Sequence Endorsement or an Adjustment in a void operation for a first endorsement, the Distributor Grid did not update, and the top-level fields were updating in the Transaction XML. Now, when performing an Out-of-Sequence Endorsement or Adjustment, the Distributor Grid fields and the top-level fields update.

  • Previously, when manually adding an Invoice in Batch Receipts using the Invoice Allocation grid, there was no option to see the details of the Charge Type in the grid. A new Charge Type column has been added under the Invoice Allocation grid to show the details of the charges for the respective Invoice.